Summary

This PR adds a new /speckit.status command that provides visibility into project and feature progress across the spec-driven development workflow.

The Gap It Fills

Currently, users have no quick way to understand:

• Which features exist and their workflow stage
• What the current active feature is
• What artifacts are complete vs. missing
• Task completion progress during implementation
• What command to run next

While /speckit.analyze checks artifact quality and consistency, /speckit.status shows progress and state.

Key Features

• Pipeline view: Shows all features with their workflow stages (specify → plan → tasks → implement)
• Artifact status: Displays which documents exist for current/selected feature
• Progress tracking: For features in implementation, shows task completion percentages
• Next action: Recommends the logical next command based on current state
• Flexible targeting: Support for --all, --verbose, --json, and --feature <name> flags

Example Output

Spec-Driven Development Status

Project: my-project
Branch: 003-user-auth
Constitution: ✓ Defined (v1.2.0)

Features
+-----------------+---------+------+-------+------------------+
| Feature         | Specify | Plan | Tasks | Implement        |
+-----------------+---------+------+-------+------------------+
| 001-onboarding  |    ✓    |  ✓   |   ✓   | ✓ Complete       |
| 002-dashboard   |    ✓    |  ✓   |   ✓   | ● 12/18 (67%)    |
| 003-user-auth < |    ✓    |  ✓   |   ○   | -                |
+-----------------+---------+------+-------+------------------+

Next: /speckit.tasks
  Generate implementation tasks from your plan

Files Added

• templates/commands/status.md - Command template with execution steps
• scripts/bash/get-project-status.sh - Discovery script (Bash)
• scripts/powershell/Get-ProjectStatus.ps1 - Discovery script (PowerShell)

Documentation Updated

• README.md - Added to Optional Commands table, updated script listings
• spec-driven.md - Added command description section

Test Plan

• Verify command template is included in release packages
• Test get-project-status.sh --json returns valid JSON
• Test with no features (empty state)
• Test with multiple features at different stages
• Test --feature flag with name, number prefix, and path
• Verify PowerShell script produces equivalent output

AI Disclosure

This PR was developed with Claude Code (Claude Opus 4.5) assistance for:

• Ideation and design of the command scope and output format
• Command template implementation following existing patterns
• Shell script implementation (Bash and PowerShell)
• Documentation updates

The design decisions were made collaboratively through discussion, and all code has been reviewed.

🤖 Generated with Claude Code